Computational fire engineering - do we have what we need?

This presentation will attempt to address the issue of whether the engineering design community has the knowledge, data and tool sets required to undertake advanced evacuation analysis. In discussing this issue I want to draw on examples not only from the building industry but more widely from where ever people come into contact with an environment fashioned by man. Prescriptive design regulations the world over suggest that if we follow a particular set of essentially configurational regulations concerning travel distances, number of exits, exit widths, etc it should be possible to evacuate a structure within a pre-defined acceptable amount of time. In the U.K. for public buildings this turns out to be 2.5 minutes, internationally in the aviation industry this is 90 seconds, in the UK rail industry this is 90 seconds and the international standard adopted by the maritime industry is 60 minutes. The difficulties and short comings of this approach are well known and so I will not repeat them here, save to say that this approach is usually littered with “magic numbers” that do not stand up to scrutiny. As we are focusing on human behaviour issues, it is also worth noting that more generally, the approach fails to take into account how people actually behave, preferring to adopt an engineer’s view of what people should do in order to make their design work. Examples of the failure of this approach are legion and include the; Manchester Boeing 737 fire, Kings Cross underground station fire, Piper Alpha oil platform explosion, Ladbroke Grove Rail crash and fire, Mont Blanc tunnel fire, Scandinavian Star ferry fire and the Station Nightclub fire.

HyperJoseph: the hypertextual organization. Epistemological considerations

HYPERJOSEPH combines hypertext, information retrieval, literary studies, Biblical scholarship, and linguistics. Dialectically, this paper contrasts hypertextual form (the extant tool) and AI-captured content (a desideratum), in the HYPERJOSEPH project. The discussion is more general and oriented to epistemology.

Powering the virtual university with standard portal technology

This article describes ongoing research on developing a portal framework based on the OASIS Web Services for Remote Portlets (WSRP) standard for integration of Web-based education contents and services made available through a model for a European Networked University. We first identify the requirements for such a framework that supports integration at the presentation level and collaboration in developing and updating study programmes and course materials. We then outline the architecture design, and report on the initial implementation and preliminary evaluation.

A design pattern for integration of business process management systems

A cross-domain workflow application may be constructed using a standard reference model such as the one by the Workflow Management Coalition (WfMC) [7] but the requirements for this type of application are inherently different from one organization to another. The existing models and systems built around them meet some but not all the requirements from all the organizations involved in a collaborative process. Furthermore the requirements change over time. This makes the applications difficult to develop and distribute. Service Oriented Architecture (SOA) based approaches such as the BPET (Business Process Execution Language) intend to provide a solution but fail to address the problems sufficiently, especially in the situations where the expectations and level of skills of the users (e.g. the participants of the processes) in different organisations are likely to be different. In this paper, we discuss a design pattern that provides a novel approach towards a solution. In the solution, business users can design the applications at a high level of abstraction: the use cases and user interactions; the designs are documented and used, together with the data and events captured later that represents the user interactions with the systems, to feed an intermediate component local to the users -the IFM (InterFace Mapper) -which bridges the gaps between the users and the systems. We discuss the main issues faced in the design and prototyping. The approach alleviates the need for re-programming with the APIs to any back-end service thus easing the development and distribution of the applications